Performance metrics 🚀

I must've missed those, I'll take a look tomorrow. And yea I'm a huge fan of everything the Point-Free guys do :)

TBH Im not a huge fan of this change. The result information should be clear in the documentation, and the function name should be clear.

Having bytes as a value type is confusing, nothing indicates that this is a number indicating the amount of bytes. This could easily be misunderstood as a collection of byte (which btw is a valid type in other languages).

Take - (bytes)freeMemory for example. Am I freeing some memory? Is this function returning the actual bytes released as a collection? What about - (bytes)freeStorage what storage in being released?
I would rather call freeMemorySize, freeStorageSize and 'appMemorySize'

We can do both. If we call it freeStorageSize then question is still "what is the unit", which has come up in multiple comments already.

IMO a simple

/**
* Returns the amount of bytes...
*/

Above the function in the header should be enough to solve this.

That being said, I will not oppose if you want to merge this. Just sharing my thoughts.

We could always add the _bytes suffix to those methods to show that is the unit that is being returned. Alternatively, we could define a struct like

NS_ENUM(NSUInteger, SentryMemoryUnit) {
  SentryMemoryUnitByte,
  SentryMemoryUnitMegabyte,
...
}

typedef struct {
  int quantity;
  SentryMemoryUnit unit;
} SentryMemorySize;

maybe overkill, just looking at alternatives. I'm mostly fine with the proposed typedef. One benefit of having the enum/struct is that doc comments can be attached that can be brought up with a doc popover in Xcode with an ⌥ + click on the names.